The case for slower interfaces

We optimised the wait out of everything, then wondered why nothing feels considered. There is a difference between an interface that is fast and one that is jumpy — and users feel it even when they cannot name it.

Watch someone sign a mortgage in an app that responds in eleven milliseconds. The speed reads as indifference. Some moments carry weight, and the interface should carry it with them.

Pace is information

A deliberate 400 milliseconds on a destructive confirmation is not latency, it is punctuation. The pause tells the user: this one matters. Stride's post-run summary fades in over half a second — not because we could not render it faster, but because arrival should feel like exhale, not interrupt.

The craft is in choosing where to spend slowness. Ninety-five percent of an interface should be instant. The remaining five percent — commitments, reveals, endings — earn their tempo. That contrast is what makes the fast parts feel fast.

Speed is table stakes. Rhythm is design.